Device and process for remote management of a network of audiovisual information reproduction systems

ABSTRACT

Management device for a network of audiovisual information reproduction systems or jukeboxes, including a database with a plurality of sets of arrays, each array containing grouped information either about the composition of a jukebox, or the use of the jukebox, or the payment of fees. The database is managed by a computer server connected with the audiovisual information reproduction systems to receive messages sent by each audiovisual information reproduction device and containing information necessary to update determined sets of arrays in the database, and update data or the program for each audiovisual information reproduction device with information stored in at least one set of arrays in the database and transmitted in this message.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 13/593,831filed Aug. 24, 2012, which is a continuation of application Ser. No.13/179,834 filed Jul. 11, 2011, which is a continuation of applicationSer. No. 12/230,254 filed Aug. 26, 2008, which is a continuation ofapplication Ser. No. 10/419,787 filed Apr. 22, 2003, which is acontinuation of application Ser. No. 09/598,170 filed Jun. 21, 2000,which claims priority to French Application No. 0005938 filed May 10,2000, the entire contents of each of which are hereby incorporated byreference in this application.

FIELD OF THE INVENTION

This invention relates to a device and a process for the management of anetwork of audiovisual information reproduction systems.

BACKGROUND OF THE INVENTION

International patent application WO 96/12255 describes a device forreproduction of audiovisual information commonly called jukebox. Thisjukebox is organized around a system unit that manages audiovisualreproduction means and means for memorizing at least one audiovisualinformation corresponding at least to the sound reproduction of onesong. The system unit also manages telecommunication means such as amodem, particularly to enable downloading of audiovisual informationfrom a host server. Management of orders for new songs and for changingsettings requires either that an operator should visit the site on whichthe jukebox is installed, or that the operator should use a computerwith a link to the host server. Furthermore, management operations thatcan be performed through the link with the host server are limited toordering new musical selections.

OBJECT AND SUMMARY OF THE INVENTION

Therefore, the purpose of this invention is to overcome thedisadvantages of prior art by proposing a device for management ofaudiovisual information reproduction systems that can be used to manageall information related to audiovisual information reproduction systemsand their operation in a simple and centralized manner.

This purpose is achieved by the fact that the device for management of anetwork of audiovisual information reproduction systems is characterizedin that it comprises a database with a plurality of sets of arrays, eacharray containing grouped information either about the composition of ajukebox, or the use of the jukebox, or the payment of fees, the databaseis managed by a computer server provided with means of connection withaudiovisual information reproduction systems to firstly receive messagessent by each audiovisual information reproduction device and containinginformation necessary to update determined sets of arrays in thedatabase, and secondly to send messages to each audiovisual informationreproduction device in order to update data or the program for eachaudiovisual information reproduction device with information stored inat least one set of arrays in the database and transmitted in thismessage.

According to another feature, a first set of arrays comprises generalinformation about the operating status of the jukebox.

According to another feature, the first set of arrays comprises a numberuniquely identifying each jukebox, the operating status of the jukebox,the password authorizing operation of the jukebox and the jukeboxinstallation date.

According to another feature, a second set of arrays in the databasecomprises information about the hardware and software composition ofeach jukebox.

According to another feature, the second set of arrays comprises a groupof tables containing all software that can be used on the jukeboxes,each program being identified by at least its name and its versionnumber.

According to another feature, the second set of arrays comprises a groupof tables containing the program names and versions installed on eachjukebox, for each given jukebox.

According to another feature, the second set of arrays comprises a groupof tables containing the list of hardware components usable in eachjukebox, each component being identified by a number, the group oftables also comprising an argument corresponding to the number of thejukebox on which the component is installed.

According to another feature, the second set of arrays comprises a groupof tables containing the descriptions of each software and/or a group oftables listing incompatibilities between the software and/or a group oftables containing descriptions of each hardware component, and/or agroup of tables listing incompatibilities between components andsoftware, and/or a group of tables containing the list of softwareassociated with hardware components.

According to another feature, a third set of arrays comprising a firstsubset contains all possible values for the different operating andsetting parameter sets for all jukeboxes, each value for a parameter setbeing identified by a unique number.

According to another feature, a second subset of the third set of arraysassociates an identifier of the operating and setting parameter setcontained in a group of tables in the first subset of the first group,for each jukebox identifier.

According to another feature, the parameter sets contain the differentpossible passwords in a first group of tables and/or the prices of songsin a second group of tables and/or the setting of a remote control of ajukebox in a third group of tables and/or the number of free songsusable in a third group of tables and/or Internet connection elements ina fourth group of tables.

According to another feature, a fourth set of tables determines the listof song numbers available on a jukebox with a given identifier number.

According to another feature, a fifth set of arrays comprises adescription of all songs, artists and albums making up a bank of songsin the database, each song being identified by a number.

According to another feature, the fifth set of arrays comprises a groupof tables containing a description of each song in the songs bank andwhether or not it is available on each jukebox, a group of tablescontaining a description of each album in the songs bank and whether ornot it is available on each jukebox, and a group of tables containing adescription of each artist or group of artists in the songs bank.

According to another feature, a sixth set of arrays comprisesinformation about the placement of a filter on each jukebox to preventdownloading of at least one song chosen by an operator.

According to another feature, the sixth set of arrays comprises aplurality of groups of tables that define all criteria for all filtersthat may be setup on each jukebox and applicable to at least onedetermined artist and/or at least one determined songs category and/orat least one determined disk publisher and/or at least one determinedsong, each filter being described in an array and identified by a uniquenumber identifying the filter.

According to another feature, the first set of arrays comprises anargument corresponding to the identifier of the filter(s) applied to thedetermined jukebox.

According to another feature, a seventh set of arrays compriseinformation about operators that own or rent each jukebox.

According to another feature, an eighth set of arrays comprises thehistory of the use of each jukebox.

According to another feature, the eighth set of arrays comprises a groupof tables containing the list of all identifiers of songs distributed oneach audiovisual information reproduction device, this array beingupdated by the server on reception of a report file, by a determinedaudiovisual information reproduction device, and containing the list ofsongs distributed on the jukebox.

According to another feature, a ninth set of arrays comprisesinformation necessary for the calculation of fees and the rental costfor each jukebox.

According to another feature, a tenth set of arrays comprises allinstructions intended to update at least one audiovisual informationreproduction device, these instructions being transmitted to theaudiovisual information reproduction device concerned by the server assoon as the audiovisual information reproduction device sets up acommunication with the server.

According to another feature, the tenth set of arrays comprises a groupof tables identifying update instructions for a determined jukebox andthe order in which the instructions must be executed on the jukeboxand/or the date starting from which the server can transmit instructionsto the jukebox.

According to another feature, the instructions contained in the eleventhset of tables are memorized before the date starting from which theserver can transmit instructions to the jukebox.

According to another feature, the tenth set of arrays comprises aplurality of groups of tables containing update instructions possible oneach jukebox, each instruction related either to an update to thesoftware, or the addition of a new album, or the addition of a new song,or the management of computer files on a jukebox, or the modification ofa jukebox operating parameter.

According to another feature, the tenth set of arrays comprises a groupof specific tables comprising all identifiers of instructions that werecorrectly transmitted to each jukebox, the group of specific tables alsocomprises at least the destination jukebox identifier and theinstruction transmission date, for each instruction identifier.

According to another feature, the tenth set of arrays comprises at leastone group of specific tables defining events triggering a giveninstructions group.

According to another feature, a first subset of an eleventh set ofarrays comprises information about setting up a promotion for thedistribution of at least one song available on each jukebox, eachpromotion being identified by a number, and in that a second subset ofthe eleventh set of arrays comprises references of the promotion(s)applicable to a given jukebox.

According to another feature, the first subset of the eleventh set ofarrays comprises at least one group of specific tables defining allsongs for which there is a promotion, and the promotion start and enddates, and the first subset of the eleventh set of arrays also comprisesa group or specific tables comprising price modifications of the songsfor which the promotion is made.

According to another feature, payment of fees due for the distributionof all songs included in the promotion is charged to the promoter whoinitiated the promotion.

According to another feature, the server comprises a module for thedisplay of information in the database in order to display at least onescreen comprising at least one information display area and/or at leastone information input area and/or at least one information selectionarea, each selection area provokes the collection of information by theserver in the database or validation of information contained in eachinput area and each display area includes the value of an argument inthe database.

A second purpose of the invention is to propose a process for themanagement of a network of audiovisual information reproduction systemsor jukebox.

This second purpose is achieved by the fact that the process for themanagement of a network of audiovisual information reproduction systemsor jukebox comprises a computer server with means of connection toinformation reproduction systems, characterized in that it comprises:

a step in which a jukebox is connected to the server to setup acommunication,

a step with transfers of at least one message from the jukebox to theserver,

a step in which the server processes the message to identify the jukeboxthat setup a communication and to update at least one table in adatabase controlling central management of the jukeboxes,

a step to search for instructions to update the jukebox, in at least onegroup of tables in the database,

a step for the construction of a message and then transfer of themessage from the server containing the update instructions found in thedatabase, to the jukebox that setup the communication.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features and advantages of this invention will become more obviousafter reading the following description with reference to the attacheddrawings in which:

FIG. 1 shows a block diagram of a system using a server according to theinvention,

FIG. 2 shows a simplified flow chart of the structure of a database ofthe server used by the system according to the invention,

FIGS. 3A to 3F show a detailed flow chart of the structure of a databaseused by the system according to the invention,

FIG. 4 shows an example of an audiovisual reproduction device,

FIGS. 5A to 5H show different arrays used to display information in thedatabase.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Before describing details of the remote management system for anaudiovisual reproduction device according to the invention, it is worthmentioning the composition of an audiovisual reproduction device and itsoperating mode.

FIG. 4 shows an example of an audiovisual information reproductiondevice. This type of device is described in particular in internationalpatent application WO 96/12255 submitted by the applicant. Preferably,but in no way restrictively, this audiovisual information reproductiondevice uses the hardware components mentioned and referenced below.

The system unit 1 with a microprocessor is a high performance PCcompatible system, the choice at the time of implementation was made foran Intel Pentium type system with at least the following memory meansand characteristics:

compatibility with the Vesa local bus,

processor cache memory: 256 kbytes,

RAM memory: 32 Mbytes,

high performance serial and parallel ports,

microprocessor controlled SVGA type graphic adapter,

SCSI/2 type bus controller,

self-powered static RAM memory.

Any other system unit with equivalent or better performances could beused in the invention.

This system unit controls and manages a sound control circuit 5, atelecommunications control circuit 4, an input control circuit 3, a massmemory control circuit 2, and a display means 62 control circuit 6. Thedisplay means are composed primarily of a SVGA type flat screen, highresolution, low radiation video monitor 62 with no interlacing. This isthe monitor that will be used for image reproduction (for example albumcovers for musical selections), and to display graphics and video clips.

Storage modules 21 using high speed, high capacity SCSI type hard disksform part of the memory means and are associated with the memory meansalready existing in the microprocessor device. These modules are usedfor the storage of audiovisual information.

A 28.8 kbps high speed telecommunications modem adapter 41 is includedto create the link with an audiovisual information distribution networkcontrolled by a host server.

For the reproduction of audio information in musical selections, thesystem comprises loudspeakers 54 into which the signal from an amplifiertuner 53 connected to a music synthesizer type electronic circuit 5 isinput, designed to accept a large number of input sources whileproviding a CD (compact disk) type quality output, for example such asthe microprocessor multimedia audio adapter such as a sound card.

The audiovisual reproduction device is provided with an input controllercircuit 3 that manages a touch screen 33 including a glass coating panelusing the “advanced surface wave technology”, and an AT type buscontroller. This touch screen placed in front of the monitor can be usedto select various selection information used by customers, and orderingand management control information used by the system manager or owner,on the video monitor display 62 or on a television screen 61. It is alsoused with an external keyboard 34 that can be connected to the systemthat is provided with a keyboard connector for this purpose, controlledby a key lock 32 through the interface circuit 3, for maintenancepurposes.

A fee payment device 35 is also connected to the input interface circuit3. Any other device can be used that enables reception of any paymentmethod by coins, tickets, tokens, magnetic cards or smart cards or acombination of payment means.

The system is installed in a steel frame or rack.

Apart from these elements, a cordless microphone 55 is connected to theaudio controller 5, to transform the audio controller into a powerfulpublic address and public information system, and possibly a karaokemachine. The system can use a system of cordless loudspeakers.

The audiovisual information reproduction device also comprises anintegrated circuit (not shown), electrically powered only when a read orwrite operation is carried out, and capable of storing the serial numberin a nonvolatile memory. The operating system can read or writeinformation on the circuit through a control circuit, particularly tokeep the jukebox serial number and the different operating parameters.This circuit is called an “Ibutton” in prior art.

The operating software in the system was generated around a library oftools and services specifically designed for the audiovisual field in amultimedia universe. This library advantageously includes a highperformance multi-task operating system that efficiently enablessimultaneous execution of multiple code fragments. This operatingsoftware enables concurrent and orderly execution, thus avoiding anyconflict between operations carried out on display means, audioreproduction means and management of telecommunication links through thedistribution network. Furthermore, this software is extremely flexible.

Throughout the rest of this description, the terms “audiovisualinformation reproduction device” and “jukebox” refer to the same object.

FIG. 1 shows a block diagram of the device according to the invention.According to prior art, each audiovisual reproduction device (100.1 to100.n) communicates with the host server 10 through itstelecommunication means, and for example a modem card 41 connected tothe telephone network 30. The host server 10 comprises communicationmeans 121, 111 for this purpose, for example such as at least one modemconnected to the telephone network. The host server 10 also comprises adatabase 11 containing all information about the operation of eachaudiovisual information reproduction device (100.1 to 100.n), in otherwords the operating parameters for the audiovisual informationreproduction device (100.1 to 100.n), its identification number, thelist of songs stored on each audiovisual information reproduction device(100.1 to 100.n), each operator being responsible for management of onegroup of audiovisual information reproduction device(s) (100.1 to100.n). The database also contains statistics about the use of eachaudiovisual information reproduction device (100.1 to 100.n), in otherwords the list of songs played and the date on which each song wasplayed, the list and date of all incidents that occurred during the useof each audiovisual information reproduction device (100.1 to 100.n),particularly when it was switched off, communication interruptions, andthe number of times that payment means refused the money input or theproposed payment. Similarly, the database comprises the list ofavailable songs stored in the host server memory means 10, theaudiovisual information necessary for reproduction of these songs, andthe setting tools necessary to install the operating system for eachaudiovisual information reproduction device (100.1 to 100.n). All theinformation contained in the database 11 is updated by means ofcommunications, for example periodic communications, with eachaudiovisual information reproduction device (100.1 to 100.n) through thetelephone network and modems for each audiovisual informationreproduction device (100.1 to 100.n) and the database or the host server10.

An example database 11 used in the device according to the inventionwill now be described with reference to FIGS. 2 and 3A to 3F. All thisinformation in the database 11 is stored in the form of arrays. Eacharray contains information about a theme or structure or particularfunction of the audiovisual information reproduction systems (100.1 to100.n, FIG. 1). Each item of information is identified by an argumentcontained in an array in the database 11. The information in one arraymay be linked to another array. This link is established when at leastone argument is common to the two arrays.

According to the invention, the database 11 comprises at least one firstset of arrays (1101, JUKEBOX, FIGS. 2 and 3A and 3E) representinginformation directly concerning the audiovisual information reproductiondevice (100.1 to 100.n, FIG. 1), for example such as its operatingstatus (JUK_STATUS, FIG. 3A), its identification number (JUK_ID, FIG.3C), or the available memory space (JUK_AVAILABLE_SPACE, FIG. 3A). Eachtable in this first set of arrays 1101 represents a audiovisualinformation reproduction device (100.1 to 100.n, FIG. 1) identified inthis table by its identification number (JUK_ID, FIG. 3A). Similarly,the information contained in the table in the first set of arrays (1101,FIG. 3A) can be updated when a message is received from a jukebox. Thisis done by the jukebox, as soon as it sets up communication with theserver (10, FIG. 1) processing the received message to see if theinformation contained in the database needs to be updated. If themessage contains information about changes to the jukebox status, theserver modifies the argument of the table in the first set of arrays(1101, FIG. 3A) of the jukebox concerned by the received changes.

This first set of arrays (1101, FIG. 3A) is related to at least onesecond set of arrays (1102, SOFTWARE, FIRMWARE, COMPONENT, FIGS. 3B and3D) representing information about hardware and software constituentsthat can be encountered on an audiovisual information reproductiondevice (100.1 to 100.n, FIG. 1). The arrays in the second set of arrays(1102, FIGS. 3B and 3D) comprise in particular the name (PGD_NAME,COD_ID, FIG. 3B), the version (PGM_VERSION, FIG. 3B) and theinstallation date (PGM_RELEASE_DT, FIG. 3B) of each software or hardwarecomponent, in the array (SOFTWARE, FIG. 3B). Each row in the secondarrays (1102, FIGS. 3B and 3D) corresponds to a software component or ahardware component. The link between at least one table in the secondset of arrays (1102, FIGS. 3B and 3D) and a table in the first set ofarrays (1101, FIGS. 3A and 3E) is made using the number of theaudiovisual information reproduction device (100.1 to 100.n, FIG. 1).Thus using this link, it is possible to the server to know all softwareand hardware components of an audiovisual information reproductiondevice (100.1 to 100.n, FIG. 1) with a given number by searching in eachsecond array for the rows containing the identification number of theaudiovisual information reproduction device number (100.1 to 100.n).

The first set of arrays (1101, FIGS. 2 and 3A and 3E) is also related toa third set of arrays (1103, JUKE_XXX, IB_XXX, FIGS. 3A and 3C)representing information about the setting of an audiovisual informationreproduction device (100.1 to 100.n, FIG. 1). A first group of arrays inthe third set of arrays (1103, IB_XXX, FIGS. 3A and 3C) contains alloperating parameters for the audiovisual information reproductionsystems (100.1 to 100.n, FIG. 1) and a second group of arrays in thethird set of arrays (1103, JUK_XXX, FIGS. 3A and 3C) associates eachjukebox with a given set of parameters contained in a group of arrays inthe third set of arrays (1103, IB_XXX, FIGS. 3A and 3C). Operatingparameters include parameters controlling the volume of the amplifierdefined for a jukebox in the tables (JUK_MIXAGE, FIG. 3A), or theparameters defined for the same jukebox in the Ibutton tables(IB_MIXAGE, FIG. 3A) table, or parameters about the price to be paid (IBand JUK_TUNE_COST) to select at least one song, or telecommunicationlink parameters (JUK_ISP) with the server (10, FIG. 1), or operatingparameters for a remote control if any for an audiovisual informationreproduction device (100.1 to 100.n, FIG. 1). These parameters aredefined for a jukebox in the (JUK_REMOTE_CONTROL, FIG. 3C) table and allremote control operating parameters for all jukeboxes are defined in the(IB_REMOTE_CONTROL, FIG. 3C) table, an audiovisual informationreproduction device (100.1 to 100.n, FIG. 1) being associated each timewith a table (JUK_TUNE_COST, IB_TUNE_COST, JUK_REMOTE_CONTROL,IB_REMOTE_CONTROL, FIG. 3C) in the third set of arrays (1103, FIGS. 3Aand 3C). Each row in a table stores operating parameters for anaudiovisual information reproduction device (100.1 to 100.n, FIG. 1)with a given number (JUK_ID, FIGS. 3A and 3C). The link between thefirst and third sets of arrays (1103, FIGS. 3A and 3C) may be made forexample using the identification number of an audiovisual informationreproduction device (100.1 to 100.n, FIG. 1). Thus, the server 10 canfind all operating parameters of an audiovisual information reproductiondevice (100.1 to 100.n, FIG. 1) with a given number by using this link,by searching in each third set of arrays (1103, FIGS. 3A and 3C) fortables containing the number (JUK_ID, FIGS. 3A and 3C) of the determinedaudiovisual information reproduction device (100.1 to 100.n, FIG. 1),then searching in the rows of these tables for the set of parameterscorresponding to the found reference. Similarly, the server can updatethe information contained in the third set of arrays (1103, FIGS. 3A and3C) when a message is received from a jukebox. This is done by theserver processing the received message immediately that a jukebox entersinto communication with the server, in order to determine if theinformation contained in the database needs to be updated. If themessage contains information about modifications to physical parameters,the server adds a new table or replaces the value supplied by themodifications in the row of the table concerned in the third set ofarrays (1103, FIGS. 3A and 3C).

The first set of arrays (1101, FIGS. 2, 3 a and 3E) is also related toat least a fourth set of arrays (1104, SONG, FIGS. 2 and 3A)representing information about songs downloaded on the audiovisualinformation reproduction systems (100.1 to 100.n, FIG. 1). Each song isidentified by a unique number (CLT_ID, FIGS. 2 and 3A) Each row in atable in the fourth set of arrays (1104, FIGS. 2 and 3A) represents asong stored on the audiovisual information reproduction device (100.1 to100.n, FIG. 1) identified by its identifier at the beginning of thetable. The jukebox periodically (for example daily) sends a message tothe server. This message contains the list of all songs installed on thejukebox. Thus, the server compares the list that it receives from theprevious list that it had received from the same jukebox and checks ifthere are any new songs. If there are, the server adds a tablecorresponding to the addition of one or more new songs in the list ofsongs available on the jukebox.

A fifth set of arrays (1105, CATALOGUE, FIGS. 2 and 3B) related to thefourth set of arrays (1104, SONG, FIGS. 2 and 3A) through the songidentification number (CLT_ID, FIGS. 2 and 3A), comprises a descriptionof each song in the database. Each row in the fifth array (1105, FIGS. 2and 3B) represents the description of a song in the database (11, FIG.1). This fifth set of arrays (1105, FIGS. 2 and 3B) in particular isused to determine whether or not a song is available to be downloaded onan audiovisual information reproduction device (100.1 to 100.n, FIG. 1)at the request of an operator. In particular, a song is not availableunless agreements have been made about copying and playing the song. Ifthese agreements have not been made, the song is present in the databasebut is not available for downloading to a jukebox. The link between thefirst set of arrays (1101, FIGS. 2 and 3A) and the fourth set of arrays(1104, FIGS. 2 and 3A) is made through the identification number(JUK_ID, FIG. 3A) of the audiovisual information reproduction device(100.1 to 100.n, FIG. 1).

The fourth set of arrays (1104, FIGS. 2 and 3A) is also related to asixth set of arrays (1106, FIGS. 2 and 3B) representing informationabout filters that an operator can use to prohibit downloading one or aplurality of songs determined by groups of specific tables. The song (orsongs) is identified by a first group of specific tables identified bythe identification number of the song(s) (FLT_CATALOGUE, FIGS. 2 and3B), or by a second group of specific tables identified by the artist'sidentification number of the song(s) (FLT_ARTIST, FIGS. 2 and 3B), or athird group of specific tables identified by the identification numberof the company that published the song(s) (FLT_LABEL, FIGS. 2 and 3B),or by a fourth group of specific tables identified by the identificationnumber of the category (FLT_CATEGORY, FIG. 3B) to which the song(s)belong. Each group of tables in a sixth set of arrays (1106, FIGS. 2 and3B) represents a given filter for a song, an artist, a disk publisher ora category. One of the tables (JUK_FILTER, FIGS. 2 and 3B) in the sixthset of arrays (1106, FIGS. 2 and 3A) is also linked to the first set ofarrays (1101, FIG. 3A) and comprises the description (JUK_DESC, FIG. 3B)of the filter assigned to each jukebox by the filter identificationnumber (JUF_ID) that is associated with the given jukebox identifier(JUK_ID) in each table (JUKEBOX, 1101, FIG. 3A). The first array (1101,FIG. 3A) also includes an argument corresponding to the filter number(JUF_ID). Thus, the filter on a given jukebox is defined by searching inthe sixth set of arrays (1106, FIGS. 2 and 3B) for the table(s)containing the filter number (JUF_ID). Similarly, an operator can assignthe same filter number to one or a plurality of audiovisual informationreproduction systems (100.1 to 100.n, FIG. 1).

The first array (1101, FIGS. 3A and 3E) is also related by theidentifier (JUK_ID) to a seventh set of arrays (1107, JUKE_LOCATION,FIG. 3A) representing information about the operators of audiovisualinformation reproduction systems (100.1 to 100.n, FIG. 1). Thisinformation comprises in particular an operator identifier (OPE_ID, FIG.3A) that accesses a table (OPERATOR, FIG. 3A) specific to each operator.Each array (WAREHOUSE, ADDRESS, CONTRACT, FIG. 3A) in the seventh set ofarrays (1107, FIG. 3A) corresponds to a table associated with a givenoperator. The relation between the first array (1101, FIG. 3A) and theseventh array (1107, FIG. 3A) is made through the operator identifier(OPE_ID). In order to achieve this, the first array (1101, FIG. 3A)therefore includes an argument (JUK_ID) used to find the associatedargument (OPE_ID) corresponding to the owner or renter operator of theaudiovisual information reproduction device (100.1 to 100.n, FIG. 1) inthe jukebox locating table (JUKE_LOCATION, FIG. 3A). Thus, in particularthis relation enables the server to determine the numbers of theaudiovisual information reproduction devices (100.1 to 100.n, FIG. 1)managed by the operator for a given operator number. The (JUKE_LOCATION,FIG. 3A) table in the seventh set of arrays (1107, FIG. 3A) alsoincludes the date (JUL_START_DT) on which the jukebox was installed forrental in the installation premises, and the expiration date of therental.

The first set of arrays (1101, FIGS. 2 and 3A and 3E) is also related toan eighth set of arrays (1108, FIGS. 3A and 3E) representing informationabout the log for an audiovisual information reproduction device (100.1to 100.n, FIG. 1). This information actually represents all events thattake place on each audiovisual information reproduction device (100.1 to100.n, FIG. 1) and in particular, every time that a song is played, arow is written in a table in the eighth set of arrays (1108, PLAY_LOG,FIG. 3A). Similarly, every time that an amount of money is inserted intothe audiovisual information reproduction device (100.1 to 100.n, FIG.1), a new row is written, for example in another array of the same type(SYSTEM_LOG, FIG. 3A). In particular, the information collected in thesearrays is used to calculate fees to be paid to the artists or publishersor writers of the played songs, and also to find out exactly what songswere played during a day, a week or a given period, on a determinedaudiovisual information reproduction device (100.1 to 100.n, FIG. 1).

For example, information about the fee calculations may be centralizedin a ninth set of arrays (1109, FIG. 3F) comprising groups of tables(JUKE_DAY_REPORT, FIG. 3F) related to the eighth set of arrays (1108,FIGS. 3E and 3A). The eighth set of arrays (1108, SYSTEM_LOG, PLAY_LOG,FIGS. 3E and 3A) is updated every time that the server receives a logfile during a communication setup between the server and a jukebox. Eachevent contained in the log file transmitted by the jukebox will beprocessed by the server. This processing consists of adding a row in oneof the tables (1108, SYSTEM_LOG, PLAY_LOG, FIGS. 3A and 3E) in theeighth set of arrays for each event. For example, events may be sortedinto two categories. The first events are songs played on the jukeboxand are memorized in the group of arrays (PLAY_LOG, FIGS. 3A, 3E and3F), and the second events are other operations that occurred on thejukebox, for example such as insertion of amounts of money in paymentmeans and are memorized in the SYSTEM_LOG group of arrays, FIGS. 3A and3E.

Similarly, a copy of a song made on a jukebox will be paid for by thepayment of a royalty to the song publisher. In order to do this, thefourth and fifth sets of arrays (1104, 1105 FIG. 3A, FIGS. 3B and 2)comprise all information necessary to determine the number of songs oneach jukebox. The fourth set of arrays (SONG, 1104, FIG. 3A) includesthe list of all songs stored on each jukebox. A first set of tables(MASTER_CATALOGUE) is used to determine the list of songs that wereinitially installed in each jukebox, the fifth set of arrays (CATALOGUE)identifies each song and in particular is used to determine the amountof the royalties for each song and the persons who will receive them.The royalty is then assigned by the use of an array (CONTRACT FIG. 3A)in the seventh set of arrays (1107, FIG. 3A).

Finally, the jukebox operator will be charged a fee for each use of thejukebox. This fixed fee is invoiced using the group of tables (1108,SYSTEM_LOG, FIGS. 3A and 3E) in the eighth set of arrays. Each table inthis group of tables corresponds to an event that occurred on eachjukebox. Thus, each time that an amount of money was inserted in ajukebox, another table was added. This eighth set of arrays is relatedto a group of tables in the ninth set of arrays (1109, JUKEBOX_REPORT,FIG. 3F) that defines the amount of money added into each jukebox foreach day and for each jukebox of an operator. Similarly, the details ofoperations carried out during the day can be determined for each jukeboxthrough another group of tables in the ninth set of arrays (1109,JUKEBOX_REPORT, FIG. 3F).

The first set of arrays (1101, FIGS. 2 and 3A and 3E) is also related toat least one tenth set of arrays (1110, INSTRUCTION FIG. 3F)representing information about instructions that will be sent to atleast one determined audiovisual information reproduction device (100.1to 100.n, FIG. 1). At least one group of tables in the tenth set ofarrays (1110, INSTRUCTION_DEF, FIG. 3F) contains a description of theinstructions (INS_DESC, FIG. 3F). Similarly, the relation between thefirst set of arrays (1101, FIGS. 2, 3A and 3F) and the tenth set ofarrays (1110, FIG. 3F) is made using the identification number (JUK.ID)of the audiovisual information reproduction device (100.1 to 100.n, FIG.1). Thus, all instructions intended for a determined audiovisualinformation reproduction device (100.1 to 100.n, FIG. 1) can becollected by the server, and downloaded on the identified jukebox, whenit sets up communication with the server. For example, theseinstructions may be an update to at least one software (INS_SOFTWARE,FIG. 3F) installed on the audiovisual information reproduction device(100.1 to 100.n, FIG. 1), downloading of new songs (INS_CATALOGUE,INS_ALBUM, FIG. 3F) ordered by the operator of the audiovisualinformation reproduction device (100.1 to 100.n, FIG. 1), or amodification of the operating parameters (INS_IBUTTON) of theaudiovisual information reproduction device (100.1 to 100.n, FIG. 1).The group of tables (1110, INSTRUCTION, FIG. 3F) containing the jukeboxidentification (JUK-ID) and an identification of the instructions(INS_ID) to be transmitted to this jukebox is systematically read by theserver 10 when an audiovisual information reproduction device (100.1 to100.n, FIG. 1) sets up a communication with the server 10 in order toverify whether or not the instructions stored in the tenth set of arrays(1110, FIG. 3F) are to be used by the audiovisual informationreproduction device (100.1 to 100.n, FIG. 1) that has just set up acommunication with the server 10. The link between the different groupsof tables in the tenth set of arrays is made using an instructionidentification number (INS_ID). The set of instructions contained in thetenth set of arrays (1110, FIG. 3F) can be prepared and stored in thedatabase before the date on which these instructions are to be appliedin practice on the jukebox. These instructions are not actually sent tothe jukebox until the required date of application when the jukebox setsup communication with the server 10.

The first set of arrays 1101 is related to at least one eleventh set ofarrays (1111, JUKE_PROMOTION, FIG. 3B) representing information aboutsetting up promotional operations on jukeboxes by JUK_ID through the(PRICING, FIG. 3B) table that indicates the access argument PRI_ID toone of the tables in the eleventh set of arrays (1111, FIG. 3B). Theseoperations consist essentially of making modifications to the prices ofsome songs installed on the jukeboxes. For example, the songs concernedby the promotions may be ordered by a promoter other than the jukeboxoperator. For example, these songs can be ordered and fees for thedistribution of these songs can be paid by the promoter rather than bythe operator. Information about songs for which a promotion is beingmade is contained in one of the eleventh arrays (1111, PRO_PACKAGE, FIG.3B). Similarly, price modifications for songs included in the promotionare contained in one of the eleventh arrays (1111, PRICING, FIG. 3B).Songs ordered by the promoter are paid for making use of a table(PRO_PACKAGE_CATALOGUE, FIG. 3B) that groups identifiers (CTL_ID) ofsongs included in the promotion. This table is related by an argument(PPK_ID, FIG. 3B) identifying groups of songs with a table (PROMOTION,FIG. 3B) containing the description of the promotion. This table(PROMOTION, FIG. 3B) can also be used to identify the promoter. Thus,during the calculation of royalties (described above) the server refersto the table (PRO_PACKAGE_CATALOGUE, FIG. 3B) to determine if theidentifiers of the songs played on a jukebox are contained in thistable. If an identifier of a song played on the jukebox belongs to thistable, then the royalty will be invoiced to the promoter correspondingto the identifier (PRO_ID, FIG. 3B) of the promotion to which the songbelongs.

A non-restrictive description of a plurality of groups of specifictables in the database will now be given, with reference to FIGS. 3A to3F.

The ACTION specific tables group belongs to the eighth set of arrays(1108, FIGS. 3A and 3F) and contains definitions of actions used in agroup of specific tables SYSTEM_LOG (described later) associated with ajukebox (JUK_ID). Each action is identified in the ACTION specifictables group by a code (ACT_CODE). Similarly, each ACTION specific tablecorresponds to a particular action. Thus for example, the ACTION tablefor which the action code (ACT_CODE) is equal to “M” contains thedescription of the action consisting of inserting a given amount in ajukebox.

The ADDRESS specific tables group belongs to the seventh set of arrays(1107, FIG. 3A) and contains all addresses of the various personsinvolved in the system according to the invention, in other wordsoperators, disk publishers, artists. Each table corresponds to adifferent address identifier (ADR_ID). One address (ADR_ADDRESS_1) maybe identical for a plurality of players and may be found in differenttables.

The ALBUM specific tables group belongs to the fifth set of arrays(1105, FIGS. 2 and 3B), and contains all information about albumscontained in the songs bank, in other words the name (ALB_NAME), themain artist (ART_ID), and the disk publisher (LAB_ID). Each album isidentified by a unique number (ALB_ID). One specific table in this groupof tables contains the identification of an album.

The ARTIST specific tables group belongs to the fifth set of arrays(1105, FIGS. 2 and 3B) and contains information about artists and/orpublishers and/or authors of songs, for example such as validations ofagreements for playing and copying of songs. One specific table in thistable group contains the identification of an artist or a publisher or awriter.

The BUG_COMPONENT, BUG_ERROR_MSG, BUG_JUKEBOX, BUG_KEYWORD, BUG_PROGRAM,BUG_REFERENCE, BUG_REPORT, BUG_SOLUTION, BUG_SUGGESTION arrays shown inFIG. 3E are used to archive, solve or propose solutions to malfunctionsthat occur in remote management of jukeboxes or in the operation ofjukebox programs or components.

The CATALOGUE specific tables group belongs to the fifth set of arrays(1105, FIGS. 2 and 3A and 3B), and contains information about songscontained in the database. A table in this group of tables identifiesthe song. In particular, each table includes a song name (CLT_SONG_NAME)and its length (CLT_LENGTH).

The CATEGORY specific tables group belongs to the fifth set of arrays(1105, FIGS. 3A and 3B) and contains the list of song categories, inother words the category name (CTG_TYPE), its description (CTG_DESC) andan identification number (CTG_ID). A category includes all songs of agiven type, for example jazz songs will be in one category, andChristmas carols in another category.

The COLLABORATOR specific tables group belongs to the eighth set ofarrays (1108, FIGS. 3A and 3B) and contains names of song writers. Anargument (COL_TYPE) will be assigned a defined value, for example W, todenote a writer. This differentiation is used for calculating royalties.

The COMMAND specific tables group, FIG. 3E, contains all commands thatare exchanged between the server and the jukebox when a communication issetup between them. A table in this tables group corresponds to acommand.

The COMPONENT specific tables group, FIG. 3B, contains the list of allhardware components that may be installed on a jukebox. In particular,each table contains the serial number (COM_SERIAL_NO) of each componentand its installation date (COM_STRAT_DT).

The COMPONENT_DEF specific tables group belongs to the second set ofarrays (1102, FIGS. 3B and 3D) and contains a precise description of allcomponents listed in the COMPONENT specific tables group. In particular,each table in this group of tables contains the cost of components(COD_COST), and the supplier identification (COD_VENDOR_CODE).

The COMPONENT_INCOMPAT specific tables group belongs to the second setof arrays (1102, FIGS. 3B and 3D) and contains information about anyincompatibilities between the various hardware components that can beinstalled on a jukebox.

The COMPONENT_UPGRADE specific tables group belongs to the second set ofarrays (1102, FIGS. 3B and 3D) and is used to keep a trace of allmodifications made to the COMPONENT_DEF specific tables group.

The CONTRACT specific tables group, FIG. 3A belonging to the seventh setof arrays 1107 is used to define the person(s) who will receive theroyalties each time that each song is played.

The CLT_CATEGORY specific tables group belongs to the fifth set ofarrays (1105, FIGS. 3A and 3B) and is used to associate a song with atleast one category defined in the CATEGORY specific tables group.

The EVENT specific tables group belongs to the tenth set of arrays(1110, FIG. 3F) and is used to put instructions into groups (definedlater) such that they are executed at a given moment defined in theEVENT_DEF specific tables group.

The EXECUTED_INSTRUCTION specific tables group belongs to the tenth setof arrays (1110, FIG. 3F) and is used to archive an instruction when ithas been executed on the jukebox concerned.

The FILE_RECEPTION specific tables group in FIG. 3E contains all textfiles received from jukeboxes during a communication between the serverand the jukebox.

The FIRMWARE specific tables group belongs to the second set of arrays(1102, FIGS. 3B and 3D) and is used to associate a hardware componentdescribed in the COMPONENT tables group and software described in thePROGRAM tables group intended to operate with the component.

The FLT_ARTIST specific tables group belongs to the sixth set of arrays(1106, FIG. 3B) and contains a definition of filters applicable toartists installed on jukeboxes. These filters are read every time that asong is to be downloaded on a jukebox, such that a song with an artistbelonging to a filter is not downloaded on the jukebox concerned by thefilter. Each table in this tables group corresponds to a given filter(JUF_ID) and a given artist (ART_ID).

The FLT_CATALOGUE specific tables group, FIG. 3B, is similar to theprevious group but the filter applies to a song.

The FLT_CATAGORY specific tables group, FIG. 3B, is similar to theprevious group but the filter applies to a song category.

The FLT_LABEL specific tables group, FIG. 3B, is similar to the previousgroup but the filter applies to a disk publisher (label).

The IBUTTON_INDEX specific tables group, FIG. 3F sets up a link betweenthe identification of an element of the Ibutton (defined above) and theidentification of the same element in the database.

The IB_CREDIT specific tables group belongs to the third set of arrays(1103, FIGS. 3A and 3C) and contains information about free credits thatcan be used on a jukebox, this information being contained in theIbutton of the jukeboxes. A credit shows the amount of money that has tobe paid before a song can be played on a jukebox. This information isused to determine the maximum available number of credits, andparticularly how many credits are available. Each table in this group oftables is applicable to a particular credit type.

The IB_ISP specific tables group belongs to the third set of arrays(1103, FIGS. 3A and 3C) and contains information necessary to enable anconnection to Internet, this information being contained in the Ibuttonof the jukeboxes. Each table in this tables group contains in particularthe connection parameters (ISP_SERVEUR_IP_ADDRESS, . . . ), the username (ISP_LOGIN_NAME), the password (ISP_PASSWORD), and the telephonenumber of the Internet Service Provider (ISP) (ISP_PHONE_NO). Each tablecorresponds to a given connection with a given service provider.

The IB_MIXAGE specific tables group belongs to the third set of arrays(1103, FIGS. 3A and 3C) and contains all information about soundsettings on a jukebox, this information being contained in the Ibuttonof the jukeboxes. A table in this tables group corresponds to a givensound setting.

The IB_OTHER_SETTING specific tables group belongs to the third set ofarrays (1103, FIGS. 3A and 3B) and contains all information about thesettings of jukeboxes contained in the Ibutton. Each table in thistables group comprises particularly the jukebox language (SET_LANGUAGE),the availability of the telephone line (SET_LINE_AVAIL_STRAT_TIME,SET_LINE_AVAIL_END_TIME) and the version of the Ibutton(SET_IB_VERSION). Each table corresponds to a set of determinedparameters.

The IB_PASSWORD specific tables group belongs to the third set of arrays(1103, FIGS. 3A and 3B) and contains passwords assigned to a jukebox sothat the jukebox can operate.

The IB_REMOTE_CONTROL specific tables group belongs to the third set ofarrays (1103, FIGS. 3A and 3B) and contains setting parameters for aremote control that can be used to make a jukebox operate. Theseparameters correspond to parameters memorized in the Ibutton of ajukebox.

The IB_TUNE_COST specific tables group belongs to the third set ofarrays (1103, FIGS. 3A and 3B), and contains the setting of prices to bepaid on a jukebox so that one or a plurality of songs can be selected.

All IB_XXX table groups contain all possible settings of a jukeboxmanaged by the system according to the invention. The assignment of aparticular setting, in other words a specific table in a group of tablesIB_XXX to a given jukebox (JUK_ID) is made through another specifictables group JUK_XXX (described later).

The INSTRUCTION specific tables group belongs to the tenth set of arrays(1110, FIG. 3F) and includes all instructions that must be transmittedto a jukebox. Each instruction is defined by a number (INS_ID) and thedestination jukebox is identified by its number (JUK_ID). Each table inthis group of tables corresponds to an instruction that is to be sent toa jukebox. Each table can also be used to determine the instruction typethrough a code (INS_CODE). Each table also comprises the date(INS_TARGET_DT) starting from which the server 10 can transmitinstructions to the jukebox. Thus, it is possible to prepare and storeinstructions to be sent to the jukebox in advance.

The INSTRUCTION_DEF specific tables group belongs to the tenth set ofarrays (1110, FIG. 3F) and comprises a description of all instructiontypes. The link between this tables group and the INSTRUCTION specifictables group is made using the instruction code INS_CODE.

The INS_ALBUM specific tables group belongs to the tenth set of arrays(1110, FIG. 3F) and contains instructions about the addition,modification or deletion of an album. Each table comprises an argument(IAL_EXECUTION_DT), that assures that the instruction corresponding tothe table has been executed in its entirety.

The INS_CATALOGUE specific tables group, FIG. 3F, is similar to theprevious specific tables group, but the instructions relate to a song.

The INS_IBUTTON specific tables group in FIG. 3F is similar to thespecific tables group described above, but the instructions concern themodification of a parameter stored in the Ibutton.

The INS_SOFTWARE specific tables group, FIG. 3F, similar to the previousspecific tables group except that the instructions concern software.

The INS_JEEP_SCRIPT specific tables group belongs to the tenth set ofarrays (1110, FIG. 3F) and includes instructions about the execution ofan order on a jukebox. An order may create, move, rename or delete afile on the jukebox. This array also comprises the command linecorresponding to the operations to be carried out.

The JUKEBOX specific tables group belongs to the first set of arrays(1101, FIGS. 2, 3A and 3E) and includes information about theinstallation of a jukebox. Each table in this tables group comprises inparticular a jukebox identification number (JUK_ID), its start up date(JUK-INSTALLATION_DT), its status (JUK_STATUT), etc. Each tablecorresponds to the description of a jukebox on the network.

The JUKEBOX_LOCATION specific tables group belongs to the seventh set ofarrays (1107, FIG. 3A) and contains all information about the locationof the jukebox and the company renting the jukebox.

The JUK_CONNECTION specific tables group can be used to archive allstart and end dates of communications between a jukebox and the server.

The JUK_CREDIT specific tables group belongs to the second set of arrays(1102, FIGS. 3A and 3B) and can be used to make a link with the specifictables group IB_CREDIT so that credits can be assigned to a particularjukebox (JUK_ID). This group of tables can also be used to archive thedifferent configurations of credits that have been validated on ajukebox, but which are no longer authorized. The current validitysetting for a given jukebox (JUK_ID) is contained in the specific tablethat has the most recent date (JCR_START_DT). Other tables are kept asarchives.

The JUK_FILTER specific tables group belongs to the sixth set of arrays(1106, FIG. 3B) and contains descriptions of all filters that areinstalled on jukeboxes. Each table in this tables group corresponds to afilter identified by a unique number (JUF_ID).

The JUK_ISP specific tables group belongs to the second set of arrays(1102, FIGS. 3A and 3C) and makes the link with the IB_ISP specifictables group to configure the connection of a particular jukebox(JUKE_ID). This tables group is also used to archive the differentconnection settings that have been validated on a jukebox, but that areno longer authorized. The current validity setting for a given jukebox(JUKE_ID) is contained in the specific table with the most recent date(JIS_START_DT). Other tables are kept as archives.

The JUK_MIXAGE specific tables group belongs to the second set of arrays(1102, FIGS. 3A and 3C) and is used to make the link between theIB_MIXAGE specific tables group and the sound setting on a specificjukebox (JUK_ID). This tables group also archives the different soundsettings that have been validated on a jukebox, but that are no longerauthorized. The setting that is currently valid for a given jukebox(JUK_ID) is contained in the specific table with the most recent date(JMI_START_DT). Other tables are kept as archives.

The JUK_OTHER_SETTING specific tables group belongs to the second set ofarrays (1102, FIGS. 3A and 3C) and makes the link between theIB_OTHER_SETTING specific tables group and the setting of a jukebox.This tables group is also used to archive the different settings thathave been validated on a jukebox, but that are no longer authorized. Thesetting that is currently valid for a given jukebox (JUK_ID) iscontained in the specific table with the most recent date(JOT_START_DT). Other tables are kept as archives.

The JUK_PASSWORD specific tables group belongs to the second set ofarrays (1102, FIGS. 3A and 3C) (and is used to make the link between theIB_PASSWORD specific tables group and a jukebox. Each table in thistables group is used to assign a set of passwords to a given jukeboxusing its number (JUK_ID). This tables group is also used to archive thedifferent sets of passwords that have been validated on a jukebox butthat are no longer authorized. The setting that is currently valid for agiven jukebox (JUK_ID) is contained in the specific table with the mostrecent date (JPW_START_DT). Other tables are kept as archives.

The JUK_PRICING specific tables group belongs to the eleventh set ofarrays (1111, FIGS. 2 and 3B) and is used to make the link between aPRICING array (described above) and a jukebox defined by its number(JUK_ID). Each table in this group of tables is used to assign apromotion period defined in the PRICING specific tables group to ajukebox identified by its identifier (JUK_ID).

The JUK_PROMOTION specific tables group belongs to the eleventh set ofarrays (1111, FIGS. 2 and 3B) and is used to make the link between thePROMOTION specific tables group (described below) and a jukebox. Eachtable in this group of tables is used to assign a particular promotion(PROD-ID) to a jukebox defined by its identifier (JUK_ID).

The JUK_REMOTE_CONTROL specific tables group belongs to the second setof arrays (1102, FIG. 3B) and is used to make the link between theIB_REMOTE_CONTROL specific tables group and a jukebox. Each table inthis tables group is used to assign a particular setting (REM_ID) to aremote control of a jukebox defined by its number (JUK_ID). This tablesgroup is also used to archive different settings of the remote controlthat have been validated on a jukebox but that are no longer authorized.

The JUK_TUNE_COST specific tables group belongs to the second set ofarrays (1102, FIGS. 3A and 3B) and is used to make the link between theIB_TUNE_COST specific tables group and a jukebox. This array is used toassign a choice of the price of particular songs (COS_ID) to a jukeboxdefined by its number (JUK_ID). This array is also used to archivedifferent price choices validated on the jukebox but that are no longerauthorized. The currently valid setting for a given jukebox (JUK_ID) iscontained in the most recent specific table (JRM_START_DT). Other tablesare kept as archives.

The LABEL specific tables group belongs to the fifth set of arrays(1105, FIGS. 3A and 3B) and describes all distribution names of diskpublishers contained in the database. Each table in this tables groupcontains in particular the identifier of the address of the diskpublisher (ADR_ID), the complete address being stored in the ADDRESSspecific tables group, an identification number (LAB_ID), and the nameof the disk publisher. Each table corresponds to a disk publisher.

The LABEL_ROYALTY specific tables group belongs to the ninth set ofarrays (1109, FIG. 3F) and contains information necessary forcalculating fees payable to disk publishers. Each table in the tablesgroup is linked particularly to the PLAY_LOG array (described later)that memorizes all distributions of songs originating on jukeboxes. Thelink is made by the jukebox identification number.

The LOGIN_SCRIPT specific tables group belongs to the second set ofarrays (1102, FIGS. 3B and 3D) and contains the startup scriptsassociated with Internet service providers.

The LOG_RECEPTION specific tables group belongs to the eighth set ofarrays (1108, FIGS. 3A and 3E) and is used to archive all log files inthe jukeboxes received by the server. Each table in this tables groupcontains in particular the number (JUK_ID) of the jukebox that sent thelog file, the reception date (LOG_RECEIVE_DT), and the transmitted file(LOG_FILE).

The MASTER specific tables group belongs to the fifth set of arrays(1105, FIGS. 3A and 3B) and defines lists of about 750 songs in the samestyle that may form a starting point for a list of songs available on ajukebox. Each table in the tables group comprises in particular anidentification number of each list (MAS_ID), a description of the list(MAS_DESC) and the type of list (MAS_TYPE). The names of songs making upthe list identified in the MASTER specific tables group is contained inthe MASTER_CATALOGUE specific tables group.

The MODEM_STRING specific tables group shown in FIG. 3E contains textstrings necessary for the initialization of jukebox modems. This arrayis related to the IB_OTHER_STRING tables group containing jukeboxsettings and particularly the modem setting.

The OPERATOR specific tables group belongs to the seventh set of arrays(1107, FIGS. 3A and 3F) and contains all information about all operatorswith a jukebox managed by the device according to the invention. Anoperator is a user who rents one or a plurality of jukeboxes. Inparticular, each table group contains a unique identifier (OPE_ID) foreach operator and the name (OPE_NAME) of each operator. Each table alsocontains a default setting that each operator would like to install inthe jukeboxes that he rents. The default setting is identified by the(COS_ID, REM_ID, CRE_ID, ISP_ID, SET_ID, MIX_ID) identifiers that relateeach table to the different tables in setting table groups(IB_TUNE_COST, IB_REMOTE_CONTROL, IB_CREDIT, IB_ISP, IB_OTHER_SETING,IN_MIXAGE) defined above.

The ORDERING specific tables group, FIG. 3A, contains all songs orderedby an operator through a jukebox, or through direct communication withthe server. Each table in this tables group corresponds to an orderedsong (CTL_ID). As soon as the song has been sent to the jukebox, thetable corresponding to the sent song is erased by the server 10.

The PACKAGE specific tables group belongs to the second set of arrays(1102, FIGS. 3B and 3D) and contains information about program groupsinstalled on jukeboxes. The composition of these groups is contained inthe PACKAGE_DEF specific tables group.

The PHONE specific tables group, FIG. 3A, contains all telephone numbersuseful for management of jukeboxes. Each table in this tables groupcontains the telephone number (PHO_NUMBER), the identification of theperson to whom the number belongs (PHO_OBJECT_SOURCE), the identifier ofthe array containing information about the holder (PHO_OBJECT_ID), thetype of line corresponding to the number (PHO_TYPE) in other wordswhether the number is a fixed telephone number, or a fax number or aportable telephone number.

The PLAY_LOG specific tables group belongs to the eighth set of arrays(1108, FIGS. 3A and 3E) and is used to archive all distributions ofsongs to jukeboxes. The tables in this tables group are updated everytime that a jukebox sends a log file to the server. Each tablecorresponds to the distribution of one song.

The PROGRAM specific tables group belongs to the second set of arrays(1102, FIGS. 3B and 3E) and contains all versions of all programs used.Each table in this tables group contains in particular the name(PGD_NAM), and the version (PGM_VERSION) of the program, but also theprogram itself (PGM_CODE_SOURCE). Each table corresponds to one versionof a program. Programs designed to run on jukeboxes are described in thePROGRAM_DEF specific tables group.

The PROMOTION specific tables group belongs to the eleventh set ofarrays (1111, FIG. 3B) and is used to describe promotions that couldapply to a jukebox. For example, a promotion might be a cost reductionor a free play of one or a plurality of given songs. Songs affected bythe promotion are listed in the PRO_PACKAGE_CATALOGUE specific tablesgroup. The promotion may be broadened to include all songs by a givenartist. In this case, the artist identifiers (ART_ID) concerned by thepromotion are contained in the PRO_PACKAGE_ARTIST specific tables group.Similarly, a promotion may contain promotions on given songs or on allsongs by an artist at the same time, and in this case a PRO_PACKAGEarray will contain an argument used to relate the PRO_PACKAGE_ARTIST andPRO_PACKAGE_CATALOGUE tables to the PROMOTION tables. Similarly, aPRO_PRICING tables group also comprises an argument used to relate thePROMOTION specific tables group to the PRICING specific tables groupcontaining a precise definition of the periods during which thepromotion is valid.

The PUBLISHER specific tables group (not shown) belongs to the ninth setof arrays (1109, FIG. 3F) and contains all information about publishers.

The PUBLISHER_ROYALTY specific tables group belongs to the ninth set ofarrays (1109, FIG. 3F) and contains all information about the payment offees to publishers of distributed songs or songs copied on a jukebox.

The REPLACEMENT_PROGRAM specific tables group belongs to the ninth setof arrays (1102, FIGS. 3B and 3D) and is used to indicate that oneprogram (PGD_NAME) is replaced by another program (REP_PGD_NAME)starting from a given date (REP_START-DT).

The SOFTWARE specific tables group belongs to the second set of arrays(1102, FIGS. 3B and 3D) and is used to make the link between a programand a jukebox on which the program is installed. Each table in thistables group is used to assign a program (PGD_NAME) to a jukebox definedby its number (JUK_ID). Each table is also used to archive the differentprogram installations that were validated on a jukebox but that are nolonger authorized. The current valid setting for a given jukebox(JUK_ID) is contained in the specific table with the most recent date(SOF_START_DT). Other tables are kept as archives.

The SONG specific tables group belongs to the fourth set of arrays(1104, FIGS. 2 and 3A) and is used to make the link between downloadedsongs and a jukebox on which songs were downloaded. Each table in thistables group is used to assign a song (CLT_ID) to a jukebox defined byits number (JUK_ID). This tables group is used to obtain a songdownloading history and determine the fees to be paid for eachdownloading. This tables group can also be used to archive differentsongs that were installed on a jukebox.

The SYSTEM_LOG specific tables group belongs to the eighth set of arrays(1108, FIGS. 3A and 3E) and contains all information transmitted byjukeboxes in log files, apart from information concerning distributionsof songs contained in the PLAY_LOG specific tables group.

The WAREHOUSE specific tables group belongs to the seventh set of arrays(1107, FIG. 3A) and is used to assign one or a plurality of jukeboxes toan operator's company. One operator may have a plurality of companies.Therefore, it is easier for the management of jukeboxes rented by thisoperator, to assign each jukebox to a company.

FIGS. 5A to 5H show different windows in which the information indatabase arrays is displayed. The server comprises a presentation moduleforming a user interface, in order to more easily manipulate informationcontained in the sets of arrays in the database of the system accordingto the invention. This module is used to display information in thedatabase in an easy to read form, but also to selectively collect thisinformation such that a user who is not familiar with the architectureof the database can access some information, even on the server.Furthermore, this module can be used to modify, add or deleteinformation in the database.

Essentially, this module displays a plurality of screens or windows eachcontaining either information display areas, or information input areas,or selection areas or buttons, on a monitor. Selection areas are usuallyrelated to procedures that in particular initiate the collection andstorage of information in the database or the validation of informationinput in input areas.

A first screen 200 shown in FIG. 5A is intended to display or manipulateall information about a jukebox. This screen 200 contains a plurality ofareas 201.1 to 201.22 that may be display areas or input areas. Each ofthese areas 201.1 to 201.22 corresponds to an argument in the JUKE-BOXarray, FIG. 3A. When a-user would like to refer to information about anexisting jukebox, he simply inputs the identification number of therequired jukebox in a first input area 201.1 and validates this input byselecting a first selection area 202. This selection triggers a searchamong all values of arguments in the JUKEBOX specific tables group, FIG.3A in the database, to find the one with an identification number thatcorresponds to the input number. Once this information has beencollected, it is displayed in the corresponding display areas 201.2 to201.22. When the user would like to create a new jukebox, he simplyinputs a number that has not yet been used in the first area 201.1corresponding to the identification number, and then validates hischoice by selecting a second save area 203. This save triggers thecreation of a new table in the JUKEBOX specific tables group, FIG. 3A,and generation of a password necessary for operation of the new jukeboxand that is displayed in the corresponding display area 201.2. Apartfrom the display areas 201.1, 201.2 corresponding to the jukebox numberand the password, the other input areas 201.3 to 201.22 are blank. Thefirst array 200 also comprises a plurality of series of selectionbuttons 204 to 207 each of which triggers the display of a new screen.These new screens will display information about the creation, update oroperation of the jukebox identified by the number input in thecorresponding area 201.1 on the first screen 200.

A first series 204 of buttons is used to setup a jukebox with previouslydefined default parameters. Selection of a first button 204.1 causes theI-button of the jukebox corresponding to the number input or displayedin the first area 201.1 to be initialized, thus this operation assigns adefault value for each operating parameter of the jukebox. A secondbutton 204.2 displays a screen (not shown) that assigns a predefinedlist of songs to the jukebox, and these songs will then be installed onthe jukebox to create the list of songs available on the jukebox. Athird button 204.3 displays a screen (not shown) that assigns apredefined list of programs to the jukebox, that will be used to operatethe jukebox.

A second series 205 of buttons is used to display the description ofcomponents of the jukebox. A first button 205.1 causes the display of ascreen (not shown) containing a plurality of fields used to displayinformation about the operator. This information is collected in theOPERATOR tables group, FIG. 3A, for the identifier of the operatorrenting or owning the jukebox. A second button 205.2 displays a screen(not shown) comprising a plurality of fields used to display informationabout programs installed on the jukebox. This information is collectedin the SOFTWARE tables group, FIG. 3B, and in the PROGRAM_DEF tablesgroup, FIG. 3D. A third button 205.3 causes the display of a screen (notshown) comprising a plurality of fields used to display informationabout hardware components installed on the jukebox. This information iscollected in the COMPONENT tables group, FIG. 3B and in theCOMPONENT_DEF tables group, FIG. 3B. A fourth button 205.4 causes thedisplay of a screen (not shown) comprising a plurality of fields used todisplay the list of songs now on order for the jukebox. This informationis collected in the ORDERING tables group, FIG. 3A. A fifth button 205.5causes the display of a second screen shown in FIG. 5B. The display ofthis screen is preceded by a collection of information in the SONGarray, FIG. 3A and the CATALOGUE array, FIG. 3B, to display the list ofsongs available on the jukebox identified by its identifier, in acombolist 211 on the second screen 210. Songs are identified by theirnumber 212 and their name 213. The numbers of all song are collected inthe SONG specific tables group, and for each song on the jukebox, theserver is provided with means of displaying the purchase date, thedelivery date, the transfer time, the song deletion date and the songname, these elements being collected in the CATALOGUE specific tables.This second screen 210 is intended for viewing only, and does notinclude an input area.

A third series 206 of buttons displays a screen used to view jukeboxoperating parameters. Each button 206.1 to 206.7 actually causes thedisplay of parameters identified in each table in the JUK_PASSWORD,JUK_TUNE_COST, JUK_REMOTE_CONTROL, JUK_MIXAGE, JUK_ISP, JUK_CREDIT,JUK_OTHER_SETTING table groups, FIGS. 3A and 3C, for which the argumentidentifying the jukebox corresponds to the identifier displayed in thefirst display area 201.1 on the first screen 200, FIG. 5A. Thus,selecting one of the buttons 206.1 to 206.7 initially triggers acollection of information in the JUK_AAA tables group corresponding tothe button, to find the table for which the jukebox identifier numbercorresponds to the required number. Information is then collected intable IB_AAA in the tables group associated with table JUK_AAA todetermine the value of parameters corresponding to the identifier of theparameter set found in the table in the JUK_AAA tables group. As anon-restrictive example, selecting a first selection button 206.1 in thethird series will trigger collection of information in the JUK_MIXAGEand IB_MIXAGE arrays, both FIG. 3A, to display sound settings for thejukebox selected in the first screen, in a third screen 220. This thirdscreen 220 is intended for viewing only, and does not have an inputarea. The various sound volume adjustment settings (maximum 221.4,volume 221.1, bass 221.2, treble 221.3) for the right and left channelsfor each area 221 a, 221 b are displayed in the display areas 221.Display areas are used to display volume settings for a microphone222.1, an auxiliary source 222.2, and background music 222.3.

A fourth series 207 of selection buttons is used to display a screen tomanage jukeboxes and particularly communications between the server andjukeboxes. A first button 207.1 causes the collection of information bythe server in the INSTRUCTION, INSTRUCTION-DEF, and INS_XXX tablegroups, FIG. 3F, to display a fourth screen 230 containing the list ofinstructions to be sent to the jukebox selected in the first screen 200,and displayed in a first display area 234. Therefore, this fourth screen230 comprises an area 231 in which previously defined instructions canbe displayed, or in which these instructions can be modified or newinstructions can be added. The fourth screen 230 comprises a save button232 used to validate instructions input or modified in the input area231 until the given send date. This validation also causes an update tothe INSTRUCTION, INSTRUCTION_DEF, and INS_XXX table groups.

A second button 207.2, provokes the collection of information in thePLAY_LOG tables group in FIG. 3A, and then displays a screen, forexample displaying the history of all songs played on a jukeboxidentified by the identifier number displayed in the first area 201.1 inthe first screen 200. After the collection of information in theSYSTEM_LOG tables group in FIG. 3A, a third button 207.3 displays ascreen, for example displaying the history of all actions executed onthe jukebox identified by the identifier number displayed in the firstarea 201.1 in the first screen 200. For examples, these actions consistof subsequently inserting an amount of money in the jukebox coin slot Afourth button 207.4 provokes the collection of information in theCOMMAND tables group, and then displays a screen for example displayingthe history of all orders that have been executed on the jukeboxidentified by the identifier number displayed in the first area 201.1 ofthe first screen 200. A fifth button 207.5 provokes the collection ofinformation in a JUK_CONNECTION tables group, and then displays a screendisplaying all connections setup between the server and the jukeboxidentified by the identifier number displayed in the first area 201.1 ofthe first screen 200 when the jukebox makes the connection with theserver. A sixth button 207.6 provokes the collection of information inthe LOG_RECEPTION tables group, FIG. 3E, and then displays a screendisplaying the history of all log files received by the server and sentby the jukebox identified by the identifier number displayed in thefirst area 201.1 of the first screen 200. A seventh button 207.7provokes the collection of information in the EXECUTED_INSTRUCTIONtables group, FIG. 3F, and then displays a screen displaying the historyof all instructions executed on the jukebox identified by the identifiernumber displayed in the first area 201.1 of the first screen 200.

A fifth screen 240 is used to update the songs bank contained in thedatabase. This screen 240 is used in particular to add albums or tomodify data in the songs bank, particularly when distribution rights areobtained and/or when songs are processed to be downloaded on jukeboxes.Therefore, this fifth screen 240 comprises essentially the input areas241.1 to 241.4 used to indicate all information about albums. Each inputarea 241 corresponds to an argument in the ALBUM array, FIG. 3A in thedatabase. A first area 241.1 contains the album identifier. A secondarea 241.2 contains the album name. A third area 241.3 contains the nameof the artist starring in the album. A fourth area 241.4 contains thename of the disk publisher. The fifth screen 240 also comprises acombolist 243 that displays the list of songs on the album identified byits identifier. Thus, validating the input by selection of a firstselection area 242 makes the server update the ALBUM array, FIG. 3A,either to modify the corresponding arguments if the input consists of amodification to an existing album, or to add a table in the tables groupwhen the input corresponds to adding a new album into the songs bank.

A sixth screen 250 is used to create lists of songs (master). Theselists can then be used as a starting point to initialize the list ofsongs available on a jukebox. The sixth screen comprises a number ofinput areas used to identify the list 251.1, for example to brieflydescribe the list 251.2 and to define the list type 251.3, in otherwords whether it is a list still being produced or a final list. Eachinput area 251.1 to 251.3 actually corresponds to an argument in theMASTER array, FIG. 3B. The sixth screen 250 also comprises a firstcombolist 252 containing the list of songs in the songs bank and asecond window 253 containing the list of songs already selected to formpart of the current list. The sixth screen 250 also comprises a savebutton 254 used to validate the list produced. This selection eitherprovokes the creation of a table in the MASTER specific tables group,FIG. 3B, and creation of a table in the MASTER_CATALOGUE specific tablesgroup for each song in a new list, FIG. 3B in the case of a new list, orprovokes the addition or deletion of a table in the MASTER_CATALOGUEspecific tables group, FIG. 3B, for an update to an existing list.

A seventh array 260 displays all rows in the PUBLISHER array. Thisparticular information collection is made by the server and is used tomanage royalties associated with each publisher. In order to do this,the seventh screen 260 comprises a combolist 261 composed of a pluralityof lines. Each line comprises a first field 261.1 representing theartist's identifier, a second field 261.2 representing the artist'sname, in other words in this case the name of the publishing company, athird field 261.3 representing the name of the publishing company'sadministrator, a fourth field 261.4 identifying whether of not thepublisher is in the catalogue, and a series of fields 261.5 to 261.9used to define whether or not the publisher allows reproduction anddistribution rights. Thus, a first field 261.5 indicates the date onwhich the written distribution authorization was granted. A second field261.6 indicates the date on which the signature is expected forauthorization. A third field 261.7 indicates the date starting fromwhich the contract for the agreement about the distribution of fieldshas been waiting for comments. A fourth field 261.8 indicates the dateon which a verbal agreement was obtained. A fifth field 261.9 indicatesthe date from which the distribution agreement is no longer valid.

A seventh screen 270 is used to make the inventory of programs used byjukeboxes. The seventh screen 270 comprises a first combolist 271 usedto display the list of program versions and if there are anyincompatibilities with other programs or hardware components. Thisinformation is displayed through information collection in the PROGRAMand PROGRAM_INCOMPACT arrays, FIG. 3D, in the database. In order to dothis, a first field 271.1 contains the program name. A second field271.2 contains the program version, a third field 271.3 contains thename of the company that distributes the program. A fourth field 271.4indicates the date on which the program will be available. A fifth field271.5 indicates the person who modified the program (if any). A sixthfield 271.6 indicates if there are any incompatibilities with otherprograms. A seventh field 271.7 indicates if there are anyincompatibilities with one or more hardware components.

A second combolist 272 displays the list-of jukebox numbers on which aprogram selected in the first window 271 is installed, and theinstallation date and possibly the deinstallation date. This informationis displayed after collecting information in the SOFTWARE specifictables group, FIG. 3B, in the database. The second window thus comprisesa first field 272.1 containing the identifier numbers of jukeboxes onwhich the program is installed. A second field 272.2 contains the dateon which the program was installed on the jukebox. A third field 272.3contains the date on which the program was deleted from the jukebox.

A third combolist 273 is used to verify if the program selected in thefirst window 271 is associated with a hardware component. Thisinformation is displayed after collecting information in the FIRMWAREand COMPONENT_DEF arrays, FIG. 3B, in the database. Thus, a first field273.1 contains the component identifier. A second field 273.2 containsthe description or name of the component. A third field 273.3 containsthe component installation date.

A fourth combolist 274 is used to verify if the program selected in thefirst window 271 has been replaced, and possibly when the program was orwill be replaced. This information is displayed after collectinginformation from the REMPLACEMENT_PROGRAMM specific tables group, FIG.3D, in the database. Thus, a first field 274.1 contains the programname. A second field 274.2 contains the program version. A third field274.3 contains the date on which the program replacement was started. Afourth field 274.4 indicates the date on which program replacement wasterminated. A fifth field 274.5 may, for example, contain a briefdescription of modifications made to the program at the time of thereplacement.

Other screens may be created on a same model as the screens describedabove to display other information contained in the database. Thedisplayed information may consist of a simple display of informationcontained in an array in the database, like for example for the firstscreen 200, or it may also be the result of a selective informationcollection, in other words the information search is made withparticular criteria, for example as for the seventh screen 260.Similarly, some screens do not necessarily include an input area, inother words these screens are used solely to view information, forexample the third screen 220.

It can be seen that the device according to the invention makes it easyto remotely control a plurality of jukeboxes from a central locationthrough a telecommunications network, for example a telephone network.

Obviously, persons with experience in the subject will realize that thisinvention can be embodied in many other specific forms without goingoutside the scope of the invention as claimed. Consequently, theseembodiments must be considered as an illustration, and can be modifiedwithin the limits defined by the field of the attached claims, and theinvention must not be restricted to the details given above.

What is claimed is:
 1. A server for use in a digital audiovisualdistribution system, the digital audiovisual distribution systemcomprising a plurality of digital jukebox devices, the digital jukeboxdevices being connectable to the server via respective networkconnections, the server comprising: a module involved in managing thedigital jukebox devices; and at least one processor configured at leastto: receive management data related to one or more components of thedigital jukebox devices, each said component being one of a hardware,software, and firmware components of a respective digital jukeboxdevice, the management data being generatable in connection with therespective digital jukebox devices; process the received management databy identifying which digital jukebox device(s) the received managementdata corresponds to, and locating update instructions for updating datain the identified digital jukebox device(s) in cooperation with themodule; and transmit the located update instructions to the identifieddigital jukebox device(s) through the digital audiovisual distributionsystem via associated network connection(s) in response to theprocessing, in order to prompt a corresponding update at the identifieddigital jukebox device(s).
 2. The server of claim 1, wherein the digitaljukebox devices each include at least one processor configured to causethe respective digital jukebox device to generate the management data ata predetermined date and/or time.
 3. The server of claim 1, wherein thedigital jukebox devices each include at least one processor configuredto process update instructions transmitted thereto and cause updates tobe installed.
 4. The server of claim 3, wherein updates are caused to beinstalled at a predetermined date and/or time.
 5. The server of claim 1,wherein the module includes a database comprising a plurality of datastructures including information relating to said management data. 6.The server of claim 5, wherein at least a first data structure stores anindication of software that is installable on the digital jukeboxdevices.
 7. The server of claim 6, wherein the indication of thesoftware that is installable on the digital jukebox devices includes aname and a version number of the software.
 8. The server of claim 5,wherein at least a second data structure stores an indication ofsoftware that is already installed on the digital jukebox devices. 9.The server of claim 5, wherein at least a third data structure stores anindication of hardware that is installable on the digital jukeboxdevices.
 10. The server of claim 5, wherein at least a fourth datastructure stores an indication of hardware that is already installed onthe digital jukebox devices.
 11. The server of claim 5, wherein at leasta fifth data structure stores a description of incompatibilities asbetween different hardware and software components.
 12. The server ofclaim 5, wherein at least a sixth data structure stores a listing ofpossible values for different sets of operating parameters and settingfor all digital jukebox devices connected to the digital audiovisualdistribution system, the possible values each being uniquelyidentifiable.
 13. The server of claim 5, wherein at least a seventh datastructure stores passwords, prices of songs, remote control settings,and/or a number of free songs.
 14. The server of claim 5, wherein atleast an eighth data structure stores a listing of songs available toeach said digital jukebox device in the digital audiovisual distributionsystem.
 15. The server of claim 5, wherein at least a ninth datastructure stores a description of all songs, artists, and albumsavailable for playback on the digital jukebox devices.
 16. The server ofclaim 5, wherein at least a tenth data structure stores informationregarding one or more operator-specified filters optionally individuallyassignable to the digital jukebox devices on a device-by-device basis,the filters preventing a download of at least one song.
 17. The serverof claim 5, wherein at least an eleventh data structure stores a historyof usage of the digital jukebox devices.
 18. The server of claim 5,wherein at least a twelfth data structure stores operator informationfor each said digital jukebox device.
 19. The server of claim 5, whereinat least a thirteenth data structure stores an order in which updateinstructions are to be processed by the digital jukebox devices.
 20. Theserver of claim 5, wherein at least a fourteenth data structure storespromotion information, the promotion information including a list ofsongs subject to a promotion, as well as promotion start and end dates,and price modifications for the songs in the list subject to thepromotion.